chore(ci): repoint push-email-notify to smtp-notify-action - #67

🏁 Script executed:

#!/bin/bash
set -eu
file=".github/workflows/push-email-notify.yml"
printf '%s\n' '--- workflow ---'
cat -n "$file"
printf '%s\n' '--- repository references ---'
rg -n --glob '*.yml' --glob '*.yaml' 'push-email-notify|github\.event\.deleted|branches:' .github || true

Repository: hyperpolymath/mylangiser

Length of output: 4665

🌐 Web query:

GitHub Actions push event branches filter deleted branch workflow github.event.deleted head_commit null

💡 Result:

In GitHub Actions, the push event can be triggered when a branch is deleted [1][2]. When this happens, the head_commit property in the webhook payload is null because there is no new commit associated with the deletion [3]. Additionally, the GITHUB_SHA and GITHUB_REF context variables often revert to the repository's default branch [4][5][2]. To prevent workflows from running unintentionally when a branch is deleted, or to explicitly handle such events, you can use conditional logic in your workflow YAML. Filtering out deleted branches To stop a workflow from running on a push event that involves a branch deletion, you can check the github.event.deleted boolean property within an if condition [1]: jobs: my-job: if: ${{!github.event.deleted }} runs-on: ubuntu-latest steps: - run: echo "This only runs if the branch was not deleted." Accessing deletion information If you specifically need to handle branch deletions, it is recommended to use the delete event rather than relying on the push event [6]. The delete event provides specific details about the deleted reference [6]: on: delete: push: jobs: handle-delete: if: github.event_name == 'delete' && github.event.ref_type == 'branch' runs-on: ubuntu-latest steps: - name: Report deleted branch run: echo "The branch ${{ github.event.ref }} was deleted." Summary of payload behavior during deletion: - github.event.deleted: true [1][3] - github.event.head_commit: null [3] - GITHUB_SHA: Reverts to the last commit on the default branch [4][2] - GITHUB_REF: Reverts to the default branch [4][2]

Citations:

• 1: https://stackoverflow.com/questions/78692595/react-to-specific-branch-getting-deleted-on-github
• 2: https://github.com/ghraw/github/docs/refs/heads/main/content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md
• 3: https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=deleted
• 4: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows
• 5: https://docs.github.com/actions/using-workflows/events-that-trigger-workflows
• 6: https://stackoverflow.com/questions/62281418/in-github-actions-is-it-possible-to-access-the-name-of-a-deleted-branch

🏁 Script executed:

#!/bin/bash
set -eu
url="https://github.com/ghraw/github/docs/main/content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md"
tmp="$(mktemp)"
trap 'rm -f "$tmp"' EXIT
curl -fsSL "$url" -o "$tmp"
rg -n -A18 -B8 'branches|deleted|head_commit|push event' "$tmp" | head -n 220

Repository: hyperpolymath/mylangiser

Length of output: 14110

🏁 Script executed:

#!/bin/bash
set -eu
url="https://github.com/ghraw/github/docs/main/content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md"
tmp="$(mktemp)"
trap 'rm -f "$tmp"' EXIT
curl -fsSL "$url" -o "$tmp"
line="$(rg -n '^## `push`' "$tmp" | cut -d: -f1 | head -n1)"
start=$((line - 2))
end=$((line + 95))
sed -n "${start},${end}p" "$tmp"

Repository: hyperpolymath/mylangiser

Length of output: 5141